<table border="0" cellpadding="2" cellspacing="0" width="100%">
<! -- //content -->
<tr>
<td><H2><font color="#336699" class="PageHeader">Installation Summary for Grid Engine</font></H2></td>
</tr>
</table>
<br><br>
<table border="0" cellpadding="2" cellspacing="0" width="100%">
<tr>
<td>

<p>To install Grid Engine and test the correct setup
of its functionality proceed with the following tasks:</font>
<ul>
<li>
<a href="#Create a Grid Engine administrator account and set up a service">Create
a Grid Engine administrator account and setup a service port</a></li>

<li>
<a href="#Create a directory and unpack the distribution">Create a directory
and unpack the distribution</a></li>

<li>
<a href="#Additional information before installing">Additional information
before installing</a></li>

<li>
<a href="#Install Grid Engine">Install Grid Engine</a></li>

<li>
<a href="#Verify installation">Verify installation</a></li>

<li>
<a href="#Using Grid Engine">Using Grid Engine</a></li>
</ul>
<p><h4><font color="#CC3300">General Overview
<a NAME="Create a Grid Engine administrator account and set up a service"></a>Create
a Grid Engine administrator account and set up a service port</font></H4>
An administrator account must be specified. The administrator can be an
existing user or a new user may be created for this task. This account
will own all of the files and it is used to configure and maintain the
cluster once the software is installed.
<br>The administrator account must exist prior to installation. We recommend&nbsp;
'<i>sgeadmin</i>' as the administrator account belonging to the '<i>adm</i>'
group.
<p>The software uses a tcp port for communication. All hosts in the cluster
must use the same port number. The port number can be set in the following
places:
<ul>
<li>
NIS (Yellow Pages) services or NIS+ database</li>

<br>Add the following to the services database (the port number does not
matter, it must be unused on your system and should be a reserved port)
<br>sge_commd&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 536/tcp&nbsp;&nbsp;&nbsp;&nbsp;
# communication port for Grid Engine</ul>

<ul>
<li>
Or, add the above manually to the /etc/services file on each machine</li>
</ul>

<p><h4><font color="#CC3300">
<a NAME="Create a directory and unpack the distribution"></a>Create a directory
and unpack the distribution</font></h4>
As the Grid Engine administrator, do the following:
<p>If you received the distribution in "pkgadd" format% mkdir &lt;your_gridengine_root_directory>
<blockquote>Install the packages with "pkgadd" on your file server (all
files will have the correct permissions and ownership)</blockquote>
or if you received the distribution in "tar.gz" format
<ul>
<li>
Create a directory for Grid Engine. This directory must be accessible to
all Grid Engine clients and execution hosts.</li>

<br>(e.g. /share/gridengine )
<br>% mkdir &lt;sge_root>
<br>% cd &lt;sge_root>
<br>&nbsp;
<li>
Unpack the distribution to this directory.</li>

<br>% gzip -dc sge_&lt;version>_common.tar.gz | tar xvf -
<br>% gzip -dc sge_&lt;version>_&lt;arch>.tar.gz | tar xvf -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
(repeat for all architectures you need)
<li>
Please verify the file permissions with the script</li>

<br>&lt;sge_root>/util/setfileperm.sh
<br>(all Grid Engine directories and files should be owned by the administrator,
some files need to be installed suid root)
<br>This script must run on a machine where user root has appropriate permissons
to chown/chmod file.
<br>This script not necessarily need to run on the qmaster machine.</ul>

<p><h4><font color="#CC3300">
<a NAME="Additional information before installing"></a>Additional information
before installing</font></h4>

<ul>
<li>
Grid Engine must be installed as root</li>

<br>The Grid Engine installation program needs to be run as root in order
to start the daemons. Root does NOT need write permission on the fileserver.
Once Grid Engine is installed, the administrator can handle all day to
day operations.
<br>&nbsp;
<li>
Machine rebooting</li>

<br>The machines DO NOT need to be rebooted as part of the Grid Engine
installation.
<br>&nbsp;
<li>
It may be more convenient to have a file with the list of hosts that will
be installed. The format for this file is one hostname per line. The names
may also be typed in manually when the installation prompts.</li>

<br>&nbsp;
<li>
If any stty commands exist in the users' startup scripts, jobs submitted
to Grid Engine may fail as there is no terminal associated with a Grid
Engine batch job. If there are stty commands, one of the following must
be done:</li>

<ul>
<li>
Remove all stty commands (and commands accessing a tty, like e.g. "biff")
from the login files</li>

<li>
Bracket the stty commands with an 'if' statement which checks for a terminal
before executing. For example:</li>

<br>#!/bin/csh
<br>tty -s&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
# checks terminal status
<br>if ($status == 0)&nbsp; # succeeds if a terminal is present
<br>&nbsp;&nbsp;&nbsp; &lt;place all stty commands in here>
<br>endif</ul>
</ul>

<p><h4><font color="#CC3300">
<a NAME="Install Grid Engine"></a>Install Grid Engine</font></h4>
The installation is a two step process. First, the Grid Engine files are
installed and configured on the master. Then, a small installation is&nbsp;
done on each execution host to configure and start the daemons, and to
add automatic daemon startup to the init area. This requires logging on
to each execution host as root and manually running the install program.
Alternatively, if there is a secure machine with root rsh access to all
machines, the execution host install can be done from a single machine.
<ul>
<li>
Step One - Install the master host</li>

<br>As root, on the master host, run:
<br>% ./install_qmaster&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
(This is a shortcut for ./inst-sge -fast -m)
<br>This will install the Grid Engine master.
<br>&nbsp;
<li>
Step Two - Install execution hosts</li>

<br>As root on the execution host machines, run:
<br>% ./install_execd&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
(This is a shortcut for ./inst-sge -fast -x)<br>
This will install the Grid Engine execution daemon.</ul>
The installation programs start the Grid Engine daemons, so at the completion
of a successful install, Grid Engine is up and running. If&nbsp; the&nbsp;&nbsp;&nbsp;&nbsp;
master host will also be an execution host execute Step Two also on the
master machine.
<p><h4><font color="#CC3300">
<a NAME="Verify installation"></a>Verify installation</font></h4>
After the installation is completed, the installation can be verified.
There are some sample scripts in $SGE_ROOT/examples/jobs.
<br>First source the proper settings file to setup the Grid Engine environment:
<br>&nbsp;
<ul>
<li>
&nbsp;C-shell</li>

<br>&nbsp;% source $SGE_ROOT/default/common/settings.csh
<li>
Bourne shell</li>

<br>$ .&nbsp; $SGE_ROOT/default/common/settings.sh</ul>
Then, to verify Grid Engine is accepting jobs, execute the following:
<blockquote>% qsub $SGE_ROOT/examples/jobs/sleeper.sh</blockquote>
You should see output similar to the following:
<blockquote>% qsub $SGE_ROOT/examples/jobs/sleeper.sh
<br>your job 1 ("Sleeper") has been submitted</blockquote>
Verify that all of the queues have been installed properly by running the
following:
<blockquote>% qstat -f&nbsp;&nbsp; (full listing of the queues)</blockquote>

<p><h4><font color="#CC3300">
<a NAME="Using Grid Engine"></a>Using Grid Engine</font></h4>
The main submit commands are qsub, qrsh and qtcsh. See the man pages for
submit(1) and qtcsh(1) for more details.
<ul>
<li>
qsub</li>

<br>In general, qsub is used for traditional batch submit, that is where
I/O is directed to a file. Note that qsub only accepts shell scripts, not
executable files. There is an application script, qs, which will allow
qsub to accept executable files directly.
<li>
qrsh</li>

<br>Qrsh acts similar to the rsh command, except that a host name is not
given. Instead, a shell script or an executable file is run, potentially
on any node in the cluster. I/O is directed back to the submitter's terminal
window. By default if the job cannot be run immediately, qrsh will not
queue the job. Using the '-now no' flag to qrsh will allow jobs to queue.
Note that I/O can be redirected with the shell redirect operators. For
example, to run the uname -a command:
<br>% qrsh uname -a
<br>The uname of some machine the scheduler selects in the cluster will
then be displayed on the submitting terminal. To redirect the output,
<br>% qrsh uname -a > /tmp/myfile
<br>The output from uname will be written to /tmp/myfile on the submitting
host. To allow the command to queue:
<br>% qrsh -now no uname -a
<br>If a suitable host is not immediately available the command will block
until a suitable host is available. At that time, the command output will
be displayed on the submitting terminal. See the qrsh(1) man page for more
details.
<li>
qtcsh</li>

<br>Grid Engine contains a modified tcsh, qtcsh which will automatically
submit jobs listed in a task file to the cluster. See the qtcsh(1) man
page for more details.</ul>
</table>
